Methods and Arrangements For Enabling Data Transmission Between a Mobile Device and a Static Destination Address

ABSTRACT

The embodiments of the present invention provide a solution for simplifying data transmission between a mobile device and a static destination address. This is achieved by introducing a new network node referred to as a VPC connector. The VPC connector is associated with a gateway of the operator network such as a GGSN. The VPC connector has access to a static first mapping between a subscriber identity associated with the mobile device and a static destination address to which the data from the mobile device should be sent. In order for the gateway to be able to route data from the mobile device to the correct static destination address, the gateway sends a dynamic second mapping between a temporary IP address of the mobile device and the subscriber identity associated with the mobile device to the network node referred to as the VPC connector. When the GGSN receives data from the temporary IP address of the mobile device, the GGSN requests information of the VPC address to which the GGSN should route that data. Since, the VPC connector can identify from which IP address the data is received, the VPC connector can then retrieve the VPC address by using the static first mapping and the dynamic second mapping.

TECHNICAL FIELD

The embodiments of the present invention relates to methods andarrangements for enabling data transmission between a mobile device anda static destination address, and in particular to a simplifiedprocedure for finding the static destination address.

BACKGROUND

Cloud computing is Internet-based computing, whereby shared resources,software, and information are provided to computers and other devices ondemand, like the electricity grid. FIG. 1 illustrates one example of acloud 10 where several computers 20 share different resources 30.

Cloud computing is a paradigm shift following the shift from mainframeto client-server in the early 1980s. Details are abstracted from theusers, who no longer have need for expertise in, or control over, thetechnology infrastructure “in the cloud” that supports them. Cloudcomputing describes a new supplement, consumption, and delivery modelfor IT services based on the Internet, and it typically involvesover-the-Internet provision of dynamically scalable and oftenvirtualized resources.

Cloud computing is a model for enabling convenient, on-demand networkaccess to a shared pool of configurable computing resources e.g.,networks, servers, storage, applications, and services that can berapidly provisioned and released with minimal management effort orservice provider interaction.

“Cloud computing” is based on virtualization, which is a method ofpartitioning one physical server computer into multiple “virtual”servers, giving each the appearance and capabilities of running on itsown dedicated machine.

To achieve a higher degree of security and control of the virtualresources the concept of “virtual private cloud” has been introduced. AVirtual Private Cloud (VPC) is a private cloud existing within a sharedor public cloud.

To set-up a VPN connection from a mobile operator to any existingenterprise network or a “cloud” takes time and is costly. A specificAccess Point Name (APN) in the mobile devices is required, and it isalso needed to configure the VPN between an operator and an enterprises.An operator gateway uses the APN for selecting which network to connectto. As an example, machine-to-machine (M2M) devices will connect to theenterprise network via a specific APN. This is illustrated in FIG. 2,where Machine-to-Machine (M2M) devices 115 of a 3G network 100 establishVirtual Private Network (VPN) connections 135 with which they canconnect Local Area Networks (LAN) 160 of different enterprise networks150. The M2M devices 110 are connected to the Internet via a gateway 120referred to as a GPRS Gateway Support Node (GGSN) in accordance with theAccess Point Name (APN) 115 of the M2M device 110. As stated the VPNconnections 135 are established with which the M2M device can connect tothe LAN of the respective enterprise networks 150. The M2M devices canthen interact with M2M applications 140 as they are located on the LAN160.

There are basically two ways a VPN can be set-up between a device and anenterprise Local Area Network (LAN):

1. A mobile device has been configured with an APN which points to theenterprise. An operator gateway, such as a GPRS Gateway Support Node,GGSN, will use this information to set-up a connection between theoperator gateway and the enterprise. To do this, the operator gatewayneeds to exchange VPN parameters before the connection can beestablished. Examples of such parameters are address to an enterpriseDynamic Host Configuration Protocol (DHCP) server, Radius Server, VPNGateway, and VPN credentials to encrypt and authenticate. The GGSN needsto be configured with this. The configuration and the parameter exchangeare often manual work which takes time and is therefore costly.2. A mobile device uses an APN which points to the Internet as thenetwork to connect to. This is used for mobile devices that would liketo reach internet and surf. No special behavior regarding provisioningof APN is needed. However, it is required to provision VPN parameters inthe mobile device and the provisioning to mobile devices is “costly”.Also the capacity demand on the mobile device increases when it has toencrypt/decrypt IP-packages and therefore a better Central ProcessingUnit (CPU) is required which increases the cost. In addition, since theCPU has to work harder due to the encryption/decryption, the CPU alsodrains the battery faster.

SUMMARY

The object of the embodiments of the present invention is to provide asolution for simplifying data transmission between a mobile device and astatic destination address.

This is achieved by introducing a network node referred to as a VPCconnector. The VPC connector is associated with a gateway of theoperator network such as a GGSN. The VPC connector has access to astatic first mapping between a subscriber identity associated with themobile device and a static destination address to which data from themobile device should be sent. The subscriber identity is stored on theSIM card inserted in the mobile device. The subscriber identity may bethe MSISDN or the IMSI and the static destination address may be a VPCaddress. In order for the gateway to be able to route data from themobile device to the correct static destination address, the gatewaysends a dynamic second mapping between a temporary IP (InternetProtocol) address of the mobile device and the subscriber identityassociated with the mobile device to the VPC connector.

When the gateway receives data from the IP address of the mobile device,the gateway requests information of the static destination address towhich the GGSN should route that data. Since, the VPC connector canidentify from which temporary IP address the data is received, the VPCconnector can then retrieve the static destination address by using thestatic first mapping and the dynamic second mapping.

According to a first aspect of embodiments of the present invention, amethod in a network node of an operator network for enabling datatransmission between a mobile device and a static destination address isprovided. The network node has access to a static first mapping betweena subscriber identity associated with the mobile device and the staticdestination address to which the data from the mobile device should besent. In the method, a gateway is provided with the static destinationaddress to which the data from the mobile device should be sent, byusing a dynamic second mapping between the subscriber identityassociated with the mobile device and a temporary IP address of themobile device and said first mapping such that the gateway can directthe data to the provided static destination address. The data isidentified to be received from the temporary IP-address of the mobiledevice.

According to a second aspect of embodiments of the present invention, anetwork node for enabling data transmission between a mobile device anda static destination address is provided. The network node has access toa static first mapping between a subscriber identity associated with themobile device and the static destination address to which the data fromthe mobile device should be sent. The network node comprises aprovisioning unit configured to provide a gateway with the staticdestination address to which the data from the mobile device should besent, by using a dynamic second mapping between the subscriber identityassociated with the mobile device and a temporary IP address of themobile device and said first mapping such that the gateway can directthe data to the provided static destination address. The data isidentified to be received from the temporary IP-address of the mobiledevice.

According to a third aspect of embodiments of the present invention amethod in a gateway of an operator network for enabling datatransmission between a mobile device and a static destination address isprovided. A network node associated with the gateway has access to astatic first mapping between a subscriber identity associated with themobile device and the static destination address to which the data fromthe mobile device should be sent. In the method, the static destinationaddress to which the data from the mobile device should be sent isobtained from the network node, by using a dynamic second mappingbetween the subscriber identity associated with the mobile device and atemporary IP address of the mobile device and said first mappingenabling the gateway to direct the data to the provided staticdestination address, wherein the data is identified to be received fromthe temporary IP-address of the mobile device. In addition, data fromthe mobile device is directed to the received static destinationaddress.

According to a fourth aspect of embodiments of the present invention, agateway of an operator network for enabling data transmission between amobile device and a static destination address is provided. A networknode associated with the gateway has access to a static first mappingbetween a subscriber identity associated with the mobile device and thestatic destination address to which the data from the mobile deviceshould be sent. The gateway comprises a receiver/transmitter unitconfigured to obtain the static destination address to which the datafrom the mobile device should be sent, by using a dynamic second mappingbetween the subscriber identity associated with the mobile device and atemporary IP address of the mobile device and said first mappingenabling the gateway to direct data, identified to be received from thetemporary IP-address of the mobile device, to the provided staticdestination address. The gateway further comprises a router configuredto direct the data from the mobile device to the received staticdestination address.

An advantage with embodiments of the present invention, is that themobile operator can offer an execution platform appearing as a cloud foran enterprise customer that uses e.g. 3GPP radio access to reach theapplications without the requirement to provision a specific APN orpassword in the M2M Device. According to embodiments of the presentinvention, the existing SIM-authentication can be re-used to find thecorrect static destination address for a specific M2M Device. Further,it is assumed that the operator domain is secure for sending packetswithin the network. This results in that the operators can save time andmoney, since no further authentication has to be performed and furtherconfiguration and parameter exchange can be avoided.

A further advantage with embodiments of the present invention is thatthe solution is protocol agnostic.

A yet further advantage with embodiments of the present invention isthat the mobile devices can be provided with dynamic addresses, alsoreferred to as temporary addresses.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates one example of a cloud where several computers sharedifferent resources according to prior art.

FIG. 2 illustrates VPN connections between M2M devices and M2Mapplications in enterprise networks according to prior art.

FIG. 3 illustrates a VPC connector in an operator domain according toembodiments of the present invention.

FIGS. 4-5 are sequence diagrams of the method according to embodimentsof the present invention.

FIGS. 6-8 are flowcharts of the method according to embodiments of thepresent invention.

DETAILED DESCRIPTION

The embodiments of the present invention will be described more fullyhereinafter with reference to the accompanying drawings, in whichpreferred embodiments of the invention are shown. The embodiments may,however, be embodied in many different forms and should not be construedas limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will be thorough andcomplete, and will fully convey the scope of the invention to thoseskilled in the art. In the drawings, like reference signs refer to likeelements.

Moreover, those skilled in the art will appreciate that the means andfunctions explained herein below may be implemented using softwarefunctioning in conjunction with a programmed microprocessor or generalpurpose computer, and/or using an application specific integratedcircuit (ASIC). It will also be appreciated that while the currentembodiments are primarily described in the fog in of methods anddevices, the embodiments may also be embodied in a computer programproduct as well as a system comprising a computer processor and a memorycoupled to the processor, wherein the memory is encoded with one or moreprograms that may perform the functions disclosed herein.

The embodiments of the present invention relate to methods andarrangements for enabling data transmission between a mobile device anda static destination address. This is achieved by introducing a networknode and to re-use the existing SIM-authentication to find a staticdestination address to which the data from the mobile device should besent.

In this specification, the mobile device is exemplified by a M2M device,such as a coffee machine or a refrigerator which can interact with anapplication at the service provider in an enterprise network. Theconnection to the application, e.g. a VPN connection, is provided over awireless network such as a 2G, 3G or 4G network. Accordingly, theconnection between the M2M device and M2M Application where the M2MApplication can be executed in a “cloud environment” may be a VPNconnection, but additional encryption for the connection is not requiredsince the SIM-authentication is performed which imply a secureconnection. If any additional encryption should be used such anencryption can be done on the application level.

Furthermore, each mobile device has a Subscriber Identity Module (SIM)card which is associated with a static destination address, i.e. theaddress of the application at the service provider in the enterprisenetwork to which the mobile device should connect. Hence, for example, acoffee machine comprising a SIM card can connect to an application inthe network of coffee provider.

When the coffee machine and the application interact, the coffeeprovider can monitor the condition of the coffee machine and detect whene.g. more coffee must be provided or when maintenance is required.

In order to simplify the procedure to set up a connection, theoperators' Subscriber Identity Module (SIM)-authentication is re-used tofind the address to which data packets from a mobile device should berouted and to which the mobile device should establish the connection.The SIM comprises subscriber information e.g. different keys used forauthentication and different subscriber identities such as IMSI and theSIM is issued and controlled by the operator. The SIM-card may either bea physical SIM-card or an equivalent SIM function based on software,i.e. no physical card. As stated above, the SIM of e.g. an M2M device isalso associated with the static destination to which the data from theM2M device should be sent.

The simplified procedure is achieved by introducing a network nodereferred to as a Virtual Private Cloud (VPC) connector which is a partof the operator domain. Based on information retrieved from theconventional SIM-authentication, the VPC connector can identify theaddress to which data packets from a mobile device should be routed.

The VPC connector is shown in FIG. 3, where it is illustrated that theVPC connector 260 is connected between a gateway 120 of the operatornetwork 275 and the cloud environment 290. The network is in thisspecification exemplified by a mobile network (e.g. a 2G, 3G or 4Gnetwork), wherein the mobile devices 110 (exemplified by M2M devices)are wirelessly connected to the gateway 120 of the network via basestations (not shown). According to embodiments of the present invention,the VPC connector 260 is configured to store a static first mappingbetween the each subscriber identity of the mobile devices and thestatic destination address 140 that the data from the respective mobiledevice should be sent to. The enterprises 150 can access their own cloudenvironment 290 via a VPN gateway 280 in this example.

Referring now to a scenario illustrated in FIGS. 4 and 5, where a VPCconnector 260 is provided 301 with a static first mapping 401 between asubscriber identity and a static destination to which data from thesubscriber of the subscriber identity should be sent. The subscriberidentity is available on the SIM card of the subscriber.

As illustrated in the sequence diagrams of FIGS. 4 and 5, a mobiledevice exemplified as an M2M device 110 establishes an initial dataconnection with the network via the gateway, exemplified as a GatewayGPRS Support Node (GGSN) 120 by using an activate PDP context procedure302. During the PDP context activation procedure 302, the mobile deviceis authenticated to the operator network by using information stored onthe SIM card e.g. in accordance with conventional methods. The mobiledevice is also assigned 303 a temporary IP address to be used for IPcommunication. A confirmation that the PDP context activation procedureis properly set up is sent 304 by the gateway to the mobile device.

When the temporary IP addressed is assigned to the mobile device and theconfirmation is sent, the gateway sends 305 session information to theVPC connector 260. The session information comprises the assigned IPaddressed associated with the subscriber identity of the SIM of themobile device. Thus, the VPC connector stores 306 a dynamic secondmapping 402 between the temporary IP address and the subscriberidentity, wherein the subscriber identity is the same type of subscriberidentity used in the static first mapping. By means of the subscriberidentity in the second mapping, a table comprising an associationbetween the temporary IP address, the subscriber identity and the staticdestination address is stored in the VPC connector. In this way, the VPCconnector has an association between the temporary IP address and thestatic destination address. It should be noted that the temporary IPaddress will be replaced with another temporary IP address when themobile device disconnects and connects again. The table is shown in FIG.5.

Now, the mobile device has an established IP connection with the networkand the mobile device can start sending 307 data to its application.When the gateway of the network receives data from the mobile device,the gateway receives also information of the IP-address from which thedata origins. Then, the gateway sends 308 a request to the VPC connectorto find the static destination address for the mobile device. In therequest, the gateway includes the IP address from which the dataorigins. Accordingly, the VPC connector is configured to investigate 309the table to find the static destination address based on the IPaddress. When the VPC connector has found the static destinationaddress, it transmits 310 the static destination address to the gateway.Now the gateway knows to which static destination address it shouldroute the data packets, which implies that data packets can be sent 311to the static destination address.

It should be noted that when the mobile device deactivates the PDPcontext i.e. removes the connection, the temporary IP-address in thesecond mapping will be set to “zero” while the static first mapping willstill be the same as before.

As mentioned above, the mobile device may be an M2M device communicatingwith an application of an enterprise in a virtual private cloud (VPC),i.e. the application is a part of the cloud. Therefore in such ascenario, the static destination address is a static VPC address.

Further, examples of subscriber identity types that may be used areInternational Mobile Subscriber Identity (IMSI) and Mobile SubscriberIntegrated Services Digital Network Number (MSISDN). It is howeverrequired that the same type of subscriber identity is used for the firstand the second mapping. It should be noted that the gateway may comprisea memory to store the second mapping which would result in that thenumber requests to the VPC connector can be avoided.

By using the embodiments of the present invention, the procedure forestablishing a connection between an M2M device and its static VPCaddress is simplified, since no additional authentication is required.

Turning now to FIG. 6 showing a gateway and a network node referred toas VPC connector according to embodiments of the present invention.

The network node 260 is referred to as a VPC connector and the VPCconnector is configured to establish a connection between a mobiledevice and a static destination address. The network node has access toa static first mapping 401 between a subscriber identity 682 associatedwith the mobile device and the static destination address 683 to whichthe data from the mobile device should be sent. Thus, this static firstmapping may be performed by the provisioning unit 640 below, implyingthat the provisioning unit may be configured to perform said staticfirst mapping. The network node 260 comprises a provisioning unit 640configured to provide a gateway with the static destination address 683to which the data from the mobile device should be sent. Theprovisioning unit 640 achieves that by using a dynamic second mapping402 between the subscriber identity 682 associated with the mobiledevice and a temporary IP address 681 of the mobile device and saidfirst mapping 401 such that the gateway can direct data to the providedstatic destination address.

The data is identified to be received from the temporary IP-address 681of the mobile device.

Therefore, the provisioning unit 640 further comprises areceiver/transmitter unit 660 configured to receive a temporary IPaddress of the mobile device from a gateway of the network uponestablishment of an initial connection between the mobile device and thenetwork, wherein the mobile device is identifiable by the subscriberidentity. The provisioning unit 640 further also a processing unit 650configured to map the received temporary IP-address 681 with thesubscriber identity 682 of the mobile device, in the dynamic secondmapping 402, wherein the receiver/transmitter unit 660 is furtherconfigured to receive from the gateway a request to find the staticdestination address for data from the mobile device identified by thetemporary IP address. The processing unit 650 is further configured tofind the static destination address via the dynamic second mapping andthe static first mapping, and the network node 260 further comprises areceiver/transmitter unit 660 configured to send the found staticdestination address 683 to the gateway.

As illustrated in FIG. 6, the network node may comprise a memory 670 forstoring the static first mapping 401 and the dynamic second mapping 402.

The network node may be included in the gateway 120 which is exemplifiedby the GGSN.

Moreover, the gateway 120 comprises a receiver/transmitter unit 630configured to obtain the static destination address to which the datafrom the mobile device should be sent. This is done by using a dynamicsecond mapping between the subscriber identity associated with themobile device and a temporary IP address of the mobile device and saidfirst mapping enabling the gateway to direct data to the provided staticdestination address. A processor 620 is configured to identify the datathat it is received from the temporary IP-address of the mobile device.Further, the gateway 120 comprises a router 610 configured to direct thedata from the mobile device to the received static destination address.

According to a further embodiment, the receiver/transmitter unit 630 isfurther configured to send to the network node the temporary IP addressof the mobile device upon establishment of an initial connection betweenthe mobile device and the network associated with the subscriberidentity of the mobile device, to receive data from the mobile devicebeing identifiable by the temporary IP address, and to send a request tofind the static destination address for the data of the mobile device.

The gateway 120 may comprise the network node 260. Further the gatewaymay be a GGSN or a Public Data Network gateway in Long Term Evolutionnetworks.

As illustrated in FIG. 7, a method in a network node of an operatornetwork for enabling data transmission between a mobile device and astatic destination address is provided in accordance with embodiments ofthe present invention. The network node has access to a static firstmapping between a subscriber identity associated with the mobile deviceand the static destination address to which the data from the mobiledevice should be sent. In the method, a gateway is provided 701 with thestatic destination address to which the data from the mobile deviceshould be sent. That is achieved by using a dynamic second mappingbetween the subscriber identity associated with the mobile device and atemporary IP address of the mobile device and said first mapping suchthat the gateway can direct data to the provided static destinationaddress. The data is identified to be received from the temporaryIP-address of the mobile device.

According to a further embodiment, the providing step further comprisesreceiving 702 a temporary IP address of the mobile device from a gatewayof the network upon establishment of an initial connection between themobile device and the network, wherein the mobile device is identifiableby the subscriber identity, mapping 703 the received temporaryIP-address with the subscriber identity of the mobile device, in thedynamic second mapping, receiving 704 from the gateway a request to findthe static destination address for data from the mobile deviceidentified by the IP address, finding 705 the static destination addressvia the dynamic second mapping and the static first mapping, and sending706 the found static destination address to the gateway.

According to a further aspect, a method in a gateway of an operatornetwork for enabling data transmission between a mobile device and astatic destination address is provided. A network node is associatedwith the gateway has access to a static first mapping between asubscriber identity associated with the mobile device and the staticdestination address to which the data from the mobile device should besent. In the method, the static destination address to which the datafrom the mobile device should be sent is obtained 801 from the networknode. That is achieved by using a dynamic second mapping between thesubscriber identity associated with the mobile device and a temporary IPaddress of the mobile device and said first mapping enabling the gatewayto direct data, identified to be received from the temporary IP-addressof the mobile device, to the provided static destination address. Datais then directed 805 from the mobile device to the received staticdestination address.

According to one embodiment, the obtaining step 801 further comprisessending 802 to the network node the temporary IP address of the mobiledevice upon establishment of an initial connection between the mobiledevice and the network associated with the subscriber identity of themobile device, receiving 803 data from the mobile device beingidentifiable by the temporary IP address, and sending 804 a request tofind the static destination address for the data of the mobile device.

Modifications and other embodiments of the disclosed invention will cometo mind to one skilled in the art having the benefit of the teachingspresented in the foregoing descriptions and the associated drawings.Therefore, it is to be understood that the embodiments of the inventionare not to be limited to the specific embodiments disclosed and thatmodifications and other embodiments are intended to be included withinthe scope of this disclosure. Although specific terms may be employedherein, they are used in a generic and descriptive sense only and notfor purposes of limitation.

1. A method in a network node of an operator network for enabling datatransmission between a mobile device and a static destination address,wherein the network node has access to a static first mapping between asubscriber identity associated with the mobile device and the staticdestination address to which data from the mobile device should be sent,the method comprising providing a gateway with the static destinationaddress to which the data from the mobile device should be sent, byusing a dynamic second mapping between the subscriber identityassociated with the mobile device and a temporary IP address of themobile device and said first mapping such that the gateway can directthe data, identified to be received from the temporary IP-address of themobile device, to the provided static destination address.
 2. The methodaccording to claim 1, wherein the providing step further comprises:receiving a temporary IP address of the mobile device from a gateway ofthe network upon establishment of an initial connection between themobile device and the network, wherein the mobile device is identifiableby the subscriber identity, mapping the received temporary IP-addresswith the subscriber identity of the mobile device, in the dynamic secondmapping, receiving from the gateway a request to find the staticdestination address for data from the mobile device identified by the IPaddress, finding the static destination address via the dynamic secondmapping and the static first mapping, and sending the found staticdestination address to the gateway.
 3. The method according to claim 1,wherein the mobile device is a machine-to-machine device.
 4. The methodaccording to claim 1, wherein the network node is included in thegateway.
 5. The method according to claim 1, wherein the gateway is aGPRS Gateway Support Node, GGSN or a public data network gateway.
 6. Themethod according to claim 1, wherein the subscriber identity is anInternational Mobile Subscriber Identity, IMSI, or Mobile SubscriberIntegrated Services Digital Network Number, MSISDN.
 7. The methodaccording to claim 1, wherein the static destination address is anEP-address.
 8. The method according to claim 7, wherein the staticIP-address is virtual private cloud IP-address.
 9. A network node forenabling data transmission between a mobile device and a staticdestination address, wherein the network node has access to a staticfirst mapping between a subscriber identity associated with the mobiledevice and the static destination address to which the data from themobile device should be sent, the network node comprising a provisioningunit configured to provide a gateway with the static destination addressto which the data from the mobile device should be sent, by using adynamic second mapping between the subscriber identity associated withthe mobile device and a temporary IP address of the mobile device andsaid first mapping such that the gateway can direct the data, identifiedto be received from the temporary IP-address of the mobile device, tothe provided static destination address.
 10. The network node accordingto claim 9, wherein the provisioning unit comprises areceiver/transmitter unit 660 configured to receive a temporary IPaddress of the mobile device from a gateway of the network uponestablishment of an initial connection between the mobile device and thenetwork, wherein the mobile device is identifiable by the subscriberidentity, a processing unit configured to map the received temporaryIP-address with the subscriber identity of the mobile device, in thedynamic second mapping, wherein the receiver/transmitter unit is furtherconfigured to receive from the gateway a request to find the staticdestination address for data from the mobile device identified by thetemporary IP address and the processing unit is further configured tofind the static destination address via the dynamic second mapping andthe static first mapping, and the receiver/transmitter unit is furtherconfigured to send the found static destination address to the gateway.11. The network node according to claim 9, wherein the network nodecomprises a memory for storing the first mapping and the second mapping.12. The network node according to claim 9, wherein the mobile device isa machine-to-machine device.
 13. The network node according to claim 9,wherein the network node is included in the gateway.
 14. The networknode according to claim 9, wherein the gateway is a GPRS Gateway SupportNode, GGSN or a public data network gateway.
 15. The network nodeaccording to claim 9, wherein the subscriber identity is anInternational Mobile Subscriber Identity, IMSI, or Mobile SubscriberIntegrated Services Digital Network Number, MSISDN.
 16. The network nodeaccording to claim 9, wherein the static destination address is anIP-address.
 17. The network node according to claim 16, wherein thestatic IP-address is virtual private cloud IP-address.
 18. A method in agateway of an operator network for enabling data transmission between amobile device and a static destination address, wherein a network nodeassociated with the gateway has access to a static first mapping betweena subscriber identity associated with the mobile device and the staticdestination address to which the data from the mobile device should besent, the method comprising: obtaining from the network node the staticdestination address to which the data from the mobile device should besent, by using a dynamic second mapping between the subscriber identityassociated with the mobile device and a temporary IP address of themobile device and said first mapping enabling the gateway to directdata, identified to be received from the temporary IP-address of themobile device, to the provided static destination address, and directingthe data from the mobile device to the received static destinationaddress.
 19. The method according to claim 18, wherein the obtainingstep further comprises: sending to the network node the temporary IPaddress of the mobile device upon establishment of an initial connectionbetween the mobile device and the network associated with the subscriberidentity of the mobile device, receiving data from the mobile devicebeing identifiable by the temporary IP address, and sending a request tofind the static destination address for the data of the mobile device.20. The method according to claim 18, wherein the gateway comprises thenetwork node.
 21. The method according to claim 18, wherein the gatewayis a GPRS Gateway Support Node, GGSN or a public data network gateway.22. A gateway of an operator network for enabling data transmissionbetween a mobile device and a static destination address, wherein anetwork node associated with the gateway has access to a static firstmapping between a subscriber identity associated with the mobile deviceand the static destination address to which the data from the mobiledevice should be sent, the gateway comprises areceiver/receiver/transmitter unit configured to obtain the staticdestination address to which the data from the mobile device should besent, by using a dynamic second mapping between the subscriber identityassociated with the mobile device and a temporary IP address of themobile device and said first mapping enabling the gateway to directdata, identified to be received from the temporary IP-address of themobile device, to the provided static destination address, and a routerconfigured to direct the data from the mobile device to the receivedstatic destination address.
 23. The gateway according to claim 22,wherein the receiver/receiver/transmitter unit further is configured tosend to the network node the temporary IP address of the mobile deviceupon establishment of an initial connection between the mobile deviceand the network associated with the subscriber identity of the mobiledevice, to receive data from the mobile device being identifiable by thetemporary IP address, and to send a request to find the staticdestination address for the data of the mobile device.
 24. The gatewayaccording to claim 22, wherein the gateway comprises the network node.25. The gateway according to claim 22, wherein the gateway is a GPRSGateway Support Node, GGSN or a public data network gateway.